scenario name
英 [səˈnɑːriəʊ neɪm]
美 [səˈnærioʊ neɪm]
网络 场景名称
双语例句
- One scenario could involve the Allthingsd team leaving to start an independent venture with a new name, while Dow Jones retains the Allthingsd brand ( and possibly the archived editorial content).
目前来看有一种可能是：AllThingsD的团队将离开公司，自己创立一个独立实体，启用新名称，而道琼斯将保留AllthingsD品牌（可能还包括其历史内容。） - The two that are important for our scenario are Name and Handler class.
对于我们的场景，两个重要的属性是Name和Handler类。 - This relates the data in the ErrorDetails file to the scenario, because the entries in the log file are preceded by the scenario name.
这就会把ErrorDetails文件中的数据与场景联系起来，因为日志文件中条目的前面就是场景名。 - A usage scenario is exactly what its name indicates& the description of a potential way your system is used.
使用方案恰如其名称所揭示的那样&描述使用系统的潜在方法。 - For the same user registry scenario, John may submit a job against the first base node without specifying user name and password.
对于相同用户注册中心方案，John可以向第一个基本节点提交作业，而不需要指定用户名和密码。 - For example, for this sample scenario you would enter the name ChineseShortMsgDP.
例如，对于此示例场景，可输入名称ChineseShortMsgDP。 - In this scenario a query gets the name and e-email address from a user, as in the following example.
如下例所示，在此情况下，查询语句获得用户的名称和电子邮件地址。 - In a scenario with multiple persistence units, the selection can be constrained by persistence unit name using an LDAP style filter.
在一个拥有多个持久性单元的场景中，可使用一个LDAP样式过滤器根据持久性单元限制选择。 - In our scenario the node name was set to ISSW2Node.
在我们的场景中，节点名设置为ISSW2Node。 - Give the argument passed in the method the scenario name for which the data will be captured in log file.
既然方法中有通过的论断，数据将会从日志文件得到场景名。 - In this particular scenario, the calculation can be changed to the expression: [ First name]|| ''|| [ Last name].
在这个特殊场景中，这个计算可以更改为表达式：[Firstname]''[Lastname]。 - If the log file contains any entries, the code creates a text file based on the scenario name and, scans the log file, and writes the entries to that text file.
如果日志文件中包含有什么条目，那么代码就会创建基于场景名的文本文件，浏览日志文件，并将条目写入到文本文件中。 - A common scenario in Web applications is form handling, where the user enters data into a Web page, data such as his or her name, address, preferences, and so on.
Web应用程序中的一种常见场景是表单处理，用户通过表单将数据输入到Web页面内，数据可以是用户的名字、地址、首选项等。 - In this particular scenario, Jane is attempting to update Maria's name, in which case a check on Jane's authority to modify the name field is launched.
在这个场景中，Jane尝试更新Maria的姓名，这触发对Jane修改name字段的权限的检查。 - In such a scenario, we won't be able to specify a "Correlation name for the new rows" Why?
在这种情况下，我们就无法指定一个“Correlationnameforthenewrows”。为什么呢？ - In this scenario, the master replicate definition needs to be created with the column name verification attribute turned off.
在这个场景中，需要在关闭列名检验属性的情况下创建主复制定义。 - This scenario considers the WebSphere TX behaviour known as object name coordination.
这个示例演示称为对象名协同的WebSphereTX行为。 - One common scenario for using custom agents is name lookups, where SAP users can be represented in an incoming message with their SAP user IDs.
使用定制代理的一个常见场景是名称查找，其中SAP用户可以以SAP用户ID的形式在进入的消息中呈现出来。 - This example demonstrates the scenario where the users choose any user name they want, but you want to know which users entered an e-mail address as a user name.
此示例演示以下这种情况：用户选择他们需要的任何用户名，但是您希望知道哪些用户输入了电子邮件地址作为用户名。 - For example, to capture a read only scenario, use@ ReadOnly as the annotation name and not@ TakeReadLock.
举例来说，为了捕获一个只读场景，用@ReadOnly作为注解名，而不要用@TakeReadLock。 - In our scenario, the subscription portlet enables adjusters to receive notification if a claim has been filed in their name.
在我们的场景中，该订阅portlet启用了调整器来接收请求声明是否已经按照名称归档的通知信息。 - Alistair has described this scenario in one of his project management patterns by the name "Sacrifice one person".
在他的众多项目管理模式中，Alistair将此命名为“牺牲一个人”。 - On the scenario page of the load test wizard, enter a name for your initial scenario.
在“负载测试向导”的“方案”页上，输入初始方案的名称。 - If you are running this sample in a cross-machine scenario, you must replace "localhost" in the preceding code with the fully-qualified name of the machine that is running the service.
如果您在跨计算机方案中运行该示例，则必须将前面代码中的“localhost”替换为运行服务的计算机的完全限定名称。